-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: document creating packages with framework bindings #9222
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Hi there 👋 It looks like this PR introduces broken links to the docs, please take a moment to fix them before merging:
Thank you 🙏 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few suggestions, but nothing blocking!
- `./link`: An `<a>` HTML tag with some default styles from your design system | ||
- `./next-js/link`: A customized version of [the Next.js `Link` component](https://nextjs.org/docs/app/building-your-application/routing/linking-and-navigating#link-component) with props that are preset to your organization's preferences |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This would sink in more for me if we added another framework:
- `./link`: ...
- `./next-js/link`: ...
- `./svelte/link`: ...
Description
We've had users ask about how to create bindings in their packages, so documenting it here.
Testing Instructions
👀